SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C#

C# static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C# code

  • All rules 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
 
Tags
    Impact
      Clean code attribute
        1. Using unsafe code blocks is security-sensitive

           Security Hotspot
        2. Not specifying a timeout for regular expressions is security-sensitive

           Security Hotspot
        3. Hard-coded secrets are security-sensitive

           Security Hotspot
        4. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        5. Deserializing objects without performing data validation is security-sensitive

           Security Hotspot
        6. Disabling ASP.NET "Request Validation" feature is security-sensitive

           Security Hotspot
        7. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        8. Using publicly writable directories is security-sensitive

           Security Hotspot
        9. Using clear-text protocols is security-sensitive

           Security Hotspot
        10. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        11. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        12. Configuring loggers is security-sensitive

           Security Hotspot
        13. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        14. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        15. Disabling CSRF protections is security-sensitive

           Security Hotspot
        16. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        17. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        18. Setting loose file permissions is security-sensitive

           Security Hotspot
        19. Using non-standard cryptographic algorithms is security-sensitive

           Security Hotspot
        20. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        21. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        22. Formatting SQL queries is security-sensitive

           Security Hotspot
        23. Hard-coded credentials are security-sensitive

           Security Hotspot
        24. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Disabling CSRF protections is security-sensitive

        consistency - conventional
        security
        Security Hotspot
        • cwe

        A cross-site request forgery (CSRF) attack occurs when a trusted user of a web application can be forced, by an attacker, to perform sensitive actions that he didn’t intend, such as updating his profile or sending a message, more generally anything that can change the state of the application.

        The attacker can trick the user/victim to click on a link, corresponding to the privileged action, or to visit a malicious web site that embeds a hidden web request and as web browsers automatically include cookies, the actions can be authenticated and sensitive.

        Ask Yourself Whether

        • The web application uses cookies to authenticate users.
        • There exist sensitive operations in the web application that can be performed when the user is authenticated.
        • The state / resources of the web application can be modified by doing HTTP POST or HTTP DELETE requests for example.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Protection against CSRF attacks is strongly recommended:
          • to be activated by default for all unsafe HTTP methods.
          • implemented, for example, with an unguessable CSRF token
        • Of course all sensitive operations should not be performed with safe HTTP methods like GET which are designed to be used only for information retrieval.

        Sensitive Code Example

        public void ConfigureServices(IServiceCollection services)
        {
            // ...
            services.AddControllersWithViews(options => options.Filters.Add(new IgnoreAntiforgeryTokenAttribute())); // Sensitive
            // ...
        }
        
        [HttpPost, IgnoreAntiforgeryToken] // Sensitive
        public IActionResult ChangeEmail(ChangeEmailModel model) => View("~/Views/...");
        

        Compliant Solution

        public void ConfigureServices(IServiceCollection services)
        {
            // ...
            services.AddControllersWithViews(options => options.Filters.Add(new AutoValidateAntiforgeryTokenAttribute()));
            // or
            services.AddControllersWithViews(options => options.Filters.Add(new ValidateAntiForgeryTokenAttribute()));
            // ...
        }
        
        [HttpPost]
        [AutoValidateAntiforgeryToken]
        public IActionResult ChangeEmail(ChangeEmailModel model) => View("~/Views/...");
        

        See

        • OWASP - Top 10 2021 Category A1 - Broken Access Control
        • CWE - CWE-352 - Cross-Site Request Forgery (CSRF)
        • OWASP - Top 10 2017 Category A6 - Security Misconfiguration
        • OWASP - Cross-Site Request Forgery
        • STIG Viewer - Application Security and Development: V-222603 - The application must protect from Cross-Site Request Forgery (CSRF) vulnerabilities.
        • PortSwigger - Web storage: the lesser evil for session tokens
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use